home *** CD-ROM | disk | FTP | other *** search
Text File | 1996-09-16 | 42.0 KB | 2,445 lines |
- 1. ALockUtils
-
-
- ALockUtils Version 1.1
-
- 15.09.1996
-
- Copyright © 1996 Janne Peräaho. All Rights Reserved.
-
-
- Copyrights Rights
-
- Introduction What is this?
- Requirements What do I need?
- Installation How to install?
- Commands How to use?
- Limitations Weak points
-
- History Done so far
- Comments Feedback
- Future To do
-
-
- 2. Copyrights
-
-
- ALockUtils Copyright © 1996 Janne Peräaho. All rights reserved.
-
-
- ALockUtils IS INFOWARE. IF YOU REGULARY USE ANY OF THE ALockUtils TOOLS
- YOU MUST INFORM ME ABOUT THAT. YOU DON'T HAVE TO PUT YOUR NAME AND
- ADDRESS IN YOUR NOTE, JUST PLAIN TEXT "I use ALockUtils too!" WILL DO.
-
- YOU MAY FREELY COPY AND SPREAD ALockUtils AS LONG AS ALL PROGRAMS IN
- ALockUtils PACKAGE REMAIN AN INTEGRATED WHOLE WHEN COPIED.
-
- BY SELLING OR ANY OTHER WAY OF GAINING FINANCIAL PROFIT AT THE COST OF
- ALockUtils IS FORBID.
-
-
- 3. Author
-
-
- Please, send comments, bug observations, and development proposals to me:
-
- ____
- |\ /| PAPER
- | \/ | MAIL
- |____| abcdefgh
-
- Janne Peräaho
- Tullimiehentie 3B19
- 90560 OULU 56
- FINLAND
-
- ____
- |\ /| ELECTRONIC
- | \/ | MAIL
- |____| 01010101
-
- Janne Peräaho
- jake@rieska.oulu.fi
-
-
- /\ HOME PAGE
- / \ _=___=___=_ 01010101
- |[]| | | | 10101010
-
- Janne Peräaho
- http://www.student.oulu.fi/~jake/
-
-
- 4. Introduction
-
-
- ALockUtils Version 1.1
-
- Introduction
-
-
- ALockUtils is an independent security system and a collection of utilities
- for ALock (Amiga security system by Trevor Andrews) at the same time.
-
- Each time you boot your Amiga, you will be asked your login ID and password.
- When ID and password are valid, boot procedure will continue and the
- ID, place (system name), date, and time of your login will be written into
- a separate log file.
-
- With the help of ALock and/or ALockUtils you can easily monitor, who is
- using your Amiga and when, and prevent unauthorized use of your Amiga
- computer.
-
- ALockUtils brings you an opportunity to use several startup-sequences
- and thus possibility of booting your Amiga with different setups.
- (For example one setup for Workbench users, one setup for Bridgeboard
- users, one setup for artists, one setup for game players, and so on.)
-
- ALockUtils contains also tools for controlling users, tools to get
- information about users, tools for sending and receiving mails, and a
- primitive drive protection system.
-
-
- 5. Requirements
-
-
- ALockUtils Version 1.1
-
- Requirements
-
-
- CPU......... 68000 or better
- KICKSTART... Version 2.04 or later
- LIBRARIES... reqtools.library Version 38 or later
- PROGRAMS.... execute, lock, more
-
- Programs execute, lock, and more can be found from your WorkBench-disk.
- Reqtools.library is not included.
-
-
- 6. Installation
-
-
- ALockUtils Version 1.1
-
- Installation
-
-
- ALockUtils-Install How to install ALockUtils
- ALock-Install How to install ALock
-
-
- 7. ALockUtils-Install
-
-
- ALockUtils Version 1.1
-
- Installation (files: ALock files)
-
-
- ALock and ALockUtils are using the following files: "passwd", "finger.log",
- and "motd". File "passwd" must always exists, "finger.log" is created
- automaticly, and "motd" may omit.
-
- Copy the contents of directory "ETC" to your "ETC"-directory.
-
-
- 8. ALock-Install
-
-
- ALockUtils Version 1.1
-
- Installation (files: ALock files)
-
-
- ALock and ALockUtils are using the following files: "passwd", "finger.log",
- and "motd". File "passwd" must always exists, "finger.log" is created
- automaticly, and "motd" may omit.
-
- Copy the contents of directory "ETC" to your "ETC"-directory.
-
-
- 9. ALockUtils manual installation
-
-
- ALockUtils Version 1.1
-
- Installation (files: ALock files)
-
-
- ALock and ALockUtils are using the following files: "passwd", "finger.log",
- and "motd". File "passwd" must always exists, "finger.log" is created
- automaticly, and "motd" may omit.
-
- Copy the contents of directory "ETC" to your "ETC"-directory.
-
-
- 10. Directories
-
-
- ALockUtils Version 1.1
-
- Installation (directories)
-
-
- ETC ETC:
- System's home HOMES:
- User's home HOME:
-
- Directories for etc, system's home, and users' homes are needed.
-
-
- 11. ETC
-
-
- ALockUtils Version 1.1
-
- Installation (directories: ETC)
-
-
- This directory contains crucial files for ALock and ALockutils.
-
- Assign "ETC:" to this directory, before calling any ALock- or ALockUtils
- commands.
-
-
- 12. System's home
-
-
- ALockUtils Version 1.1
-
- Installation (directories: System's home)
-
-
- System should have an own directory, where all users' home directories,
- lock files, and individual MOTD files are.
-
- Assign "HOMES:" to this directory, before calling any ALockUtils commands.
-
-
- 13. User's home
-
-
- ALockUtils Version 1.1
-
- Installation (directories: User's home)
-
-
- Every user have an own home directory. Home directory is located at system's
- home. Say we have user with user ID "jake" and system's home directory is
- located at "S:homes/". This user's home directory will therefore be
- "S:homes/jake/".
-
- When user logs into a system (ALock & UserStartup and Login commands),
- device "HOME:" is assigned to user's home directory.
-
- Use command HomeAdd to create new home directory.
-
-
- 14. Files
-
-
- ALockUtils Version 1.1
-
- Installation (files)
-
-
- ALock files How to install crucial files
- Commands How to install commands
- Drive locks How to install drive locks
- Mailbox How to install mailboxes
- MOTDs How to install MOTDs
- Startup-sequences How to install startup sequences
-
- ALock utilities assume that certain files exists. Like mailbox, drive lock,
- startup,and motd files.
-
-
- 15. ALock files
-
-
- ALockUtils Version 1.1
-
- Installation (files: ALock files)
-
-
- ALock and ALockUtils are using the following files: "passwd", "finger.log",
- and "motd". File "passwd" must always exists, "finger.log" is created
- automaticly, and "motd" may omit.
-
- Copy the contents of directory "ETC" to your "ETC"-directory.
-
-
- 16. Commands
-
-
- ALockUtils Version 1.1
-
- Installation (commands)
-
-
- ALockUtils directory C contains all ALockUtils commands. Copy those commands
- somewhere along system's path.
-
-
- 17. Drive locks
-
-
- ALockUtils Version 1.1
-
- Installation (drive locks)
-
-
- Superuser can write protect drives from users. In system's home directory
- ("HOMES:") every user have an own lock file containing the name of the
- drives which should be write protect when user logs in. Lock file name is
- "lock.<id>", where <id> is the user login ID.
-
- Say we have an user with user ID "jake" and we want to lock drives DH1: and
- DH2: from that user. All we need to do, is to create file "lock.jake" in
- system's home ("HOMES:") directory and write two lines in that file:
-
- DH1:
- DH2:
-
- and that's it!
- Drives are locked when UserStartup command or Login command is
- succesfully executed. Locking is not permanent. Either reboot or new login
- (Login command) will release the locks.
-
- When home directory is created with HomeAdd command with option LOCKS,
- empty lock file is created. After creating the lock file, use any text
- editor to add drive names (which should be locked) in that file.
-
-
- 18. Mailbox
-
-
- ALockUtils Version 1.1
-
- Installation (mailbox)
-
-
- Each user have an own mailbox. Mailbox is located at "HOME:mail/incoming".
- Mailbox contains several mails which all have a same format:
-
- From: <id>@<host><LF>
- Subject: <subject><LF>
- To: <id> (<real_name>)<LF>
- Date: <weekday> <month> <day> <hour>:<minutes>:<seconds> <year><LF>
- <message><FF>
-
- where
-
- <id>
- User ID
-
- <host>
- Host name
-
- <subject>
- Mail subject
-
- <real_name>
- User real name
-
- <weekday>
- Weekday (Mon, Tue, Wed...)
-
- <month>
- Month (Jan, Feb, Mar...)
-
- <day>
- Day (01-31)
-
- <hour>
- Hour (00-23)
-
- <minutes>
- Minutes (00-59)
-
- <seconds>
- Seconds (00-59)
-
- <year>
- Year (1-)
-
- <message>
- Mail text
-
- <LF>
- Line feed (ASCII value 10 ($0A))
-
- <FF>
- Form feed (ASCII value 12 ($0C)). This serves as end of mail mark.
-
-
- When home directory is created with HomeAdd command, mailbox is created
- automaticly. Don't try to create mailbox by your self. Use command HomeAdd!
-
-
- 19. MOTDs
-
-
- ALockUtils Version 1.1
-
- Installation (MOTDs)
-
-
- There are two kind of MOTD (Message Of ToDay) files: global and individuals.
- Global MOTD is shown to everyone and individual MOTD is personal and
- different for each user.
-
- ALock can show only global MOTD, but Login can show both.
-
- Global MOTD is located at "ETC:motd" and its a normal ASCII text file.
- Individual MOTD files can be found from system's home ("HOMES:") with name
- "motd.<id>", where <id> is user ID. An example of individual MOTD file:
-
- You are logged in as '286' - PC-Task user.
- Other emulators available in this system:
-
- BridgeBoard Login: 386 Password: 386
- A64 Login: c64 Password: c64
-
- The length of individual MOTD file is not limited.
- If MOTD file (global or individual) does not exists it's not been shown
- either.
-
- When home directory is created with HomeAdd command with option MOTD,
- empty MOTD file is created. Use any text editor to edit the "message of
- today".
-
-
- 20. Startup-sequences
-
-
- ALockUtils Version 1.1
-
- Installation (files: Startup-sequences)
-
-
- Individual startup-sequences
- Original startup-sequence
- Shell-Startup
-
- Installation to the original startup-sequence must be done. If you want
- to use multiple startup-sequences installation of individual startup-
- sequences is required.
-
-
- 21. Individual startup-sequences
-
-
- ALockUtils Version 1.1
-
- Installation (files: Individual startup-sequences)
-
-
- Each system user can have an own individual startup sequence. Individual
- startup sequence is an AmigaDOS script file (like startup-sequence)
- containing AmigaDOS commands.
-
- Startup file is located at user's home ("HOME:startup" = HOMES:<id>/startup)
- directory. If you have low memory and want to use for example PC-Task PC
- emulator (demo version, located at "DH1:Emulators/PC/PC-Task/"), create new
- user with name "286" and write into his/her startup file the following
- lines:
-
- ; This is an individual startup sequence for PC-Task users
- DH1:Emulators/PC/PC-Task/PC-TaskDemo
-
- Every time user "286" logs in, only PC-Task emulator will be executed.
- You save time and memory!
-
- NOTE! When command "Login" or "UserStartup" has ended and individual startup
- sequence has been executed, the execution of original startup sequence will
- continue. Therefore Login or UserStartup must be the last command in
- original startup sequence.
-
- When home directory is created with HomeAdd command with option STARTUP,
- empty startup file is created. Use any text editor to add AmigaDOS commands
- in it.
-
-
- 22. Original startup-sequence
-
-
- ALockUtils Version 1.1
-
- Installation (files: Startup-sequence)
-
-
- Edit file "S:Startup-Sequence" or "S:User-startup" and add line to execute
- "Login"-command.
-
- "Login"-command needs certain environment variables to work properly. It
- also sets new variables. Assigns to devices "ETC:" and "HOMES:" are also
- needed.
-
- Creation of "ENV:" device and assigns to "ETC:" and "HOMES:" must therefore
- occur before calling "Login". For example (S:Startup-Sequence):
-
- ...
- C:MAKEDIR RAM:T RAM:CLIPBOARDS RAM:ENV RAM:ENV/SYS <--- ENV:
- C:COPY >NIL: ENVARC: RAM:ENV ALL NOREQ <--- ENV:
- ASSIGN >NIL: ENV: RAM:ENV <--- ENV:
- ...
-
- ;BEGIN ALockUtils
- Assign ETC: SYS:ALock/etc <--- Assign ETC:
- Assign HOMES: SYS:ALock/homes <--- Assign HOMES:
- Login LOGIN="root" NOMENU <--- Call Login
- ;END ALockUtils
-
- EndCLI >NIL:
-
- Installation script installs "Login"-command to the "S:User-Startup". You
- can do the same by adding lines:
-
- ;BEGIN ALockUtils
- Assign ETC: SYS:ALock/etc <--- Assign ETC:
- Assign HOMES: SYS:ALock/homes <--- Assign HOMES:
- Login LOGIN="root" NOMENU <--- Call Login
- ;END ALockUtils
-
- to the end of "S:User-Startup"-file.
-
-
- 23. Shell-Startup
-
-
- ALockUtils Version 1.1
-
- Installation (files: Shell-Startup)
-
-
- When new shell is opened the contents of file "S:Shell-Startup" is executed.
- If you want that your mailbox is checked each time you start new shell
- process, edit "S:Shell-Startup" file and add there command:
-
- NewMail NOGUI
-
-
- 24. Environment variables
-
-
- ALockUtils Version 1.1
-
- Installation (environment variables)
-
-
- The following environment variables are used:
-
- HostName - user sets
- Kickstart - system sets
- UserID - ALockPatch and Login sets
- UserName - ALock and Login sets
- Workbench - system sets
-
- The only variable you must set is "HostName" all others are created
- automaticly. Use command HostName to set "HostName".
-
-
- 25. Commands
-
-
- ALockUtils Version 1.1
-
- Commands
-
-
- All commands
-
- ALockPatch Finger FlushLog HomeAdd
- HomeDel HostName Last ListUsers
- Login Mail MailBox NewMail
- Passwd ReadMail ReadMOTD TrashMail
- UserAdd UserDel UserMod UserStartup
- WhoAmI WhoIs
-
- Commands in groups
-
- Information Loging in Mailing Misc
- Users
-
-
- 26. Information
-
-
- ALockUtils Version 1.1
-
- Commands (information commands)
-
-
- Finger Hostname Last ListUsers MailBox NewMail
- WhoAmI WhoIs ReadMOTD
-
- Commands for information.
-
-
- 27. Loging in
-
-
- ALockUtils Version 1.1
-
- Commands (loging in commands)
-
-
- FlushLog Last Login UserStartup
-
- Commands for login procedure.
-
-
- 28. Mailing
-
-
- ALockUtils Version 1.1
-
- Commands (mailing commands)
-
-
- Mail MailBox NewMail ReadMail TrashMail
-
- Commands for mailing.
-
-
- 29. Other commands
-
-
- ALockUtils Version 1.1
-
- Commands (other commands)
-
-
- AlockPatch FlushLog HostName
-
- Miscellaneus commands.
-
-
- 30. Users
-
-
- ALockUtils Version 1.1
-
- Commands (user commands)
-
-
- Finger HomeAdd HomeDel Last ListUsers
- UserAdd UserDel UserMod Passwd UserStartup
- WhoAmI WhoIs
-
- Commands connection to users.
-
-
- 31. ALockPatch
-
-
- NAME
-
- ALockPatch
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file passwd
-
-
- Files:
-
- "ETC:passwd" - to get current user login ID
-
-
- Environment variables
-
- "UserName" - to get current user name
-
-
- DESCRIPTION
-
- ALockPatch patches ALock security system by creating environment variable
- "UserID". This variable contains current user's login ID.
-
- ALockPatch should be executed in startup-sequence just after ALock.
- If several user have a same name (real name) it is uncertain if "UserID"
- is set correctly.
-
-
- ARGUMENTS
-
- ALockPatch
-
-
- EXAMPLES
-
- ALockPatch
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- -
-
-
- 32. Finger
-
-
- NAME
-
- Finger
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to get contents of files "passwd" and "finger.log"
-
-
- Files:
-
- "ETC:passwd" - to get user real name
- "ETC:finger.log" - to get last login
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Finger gives information about current user or any other user.
-
-
- ARGUMENTS
-
- Finger ID
-
- ID
- <login_id>
- User's login ID you want to get information.
-
- Without any arguments Finger shows information about current user.
-
-
- EXAMPLES
-
- Finger
- Finger jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- ListUsers
- WhoAmI
- WhoIs
-
-
- 33. FlushLog
-
-
- NAME
-
- FlushLog
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file finger.log
-
-
- Files:
-
- "ETC:finger.log" - to flush file "finger.log"
-
-
- Environment variables:
-
- "UserID" - to set new log size
-
-
- DESCRIPTION
-
- FlushLog updates system's logfile.
- This command should be executed in a startup-sequence after ALock.
-
- FlushLog uses preference file ("FlushLog.prefs") if present. Only
- superuser can change preferences.
-
-
- ARGUMENTS
-
- FlushLog SIZE/N
-
- SIZE
- <int_number>
- Sets new limit for login history. Option available only for superuser.
-
- Without any arguments FlushLog updates logfile ("ETC:finger.log") by
- removing login information (starting from oldest), until only <logsize>
- entries are left.
-
-
- EXAMPLES
-
- FlushLog
- FlushLog 10
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Last
- Login
-
-
- 34. HomeAdd
-
-
- NAME
-
- HomeAdd
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - for passwd file
-
-
- Files:
-
- "ETC:passwd" - to get target ID real name
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
- "HostName" - to get system's name
-
-
- DESCRIPTION
-
- Superuser command only.
-
- Create home directory for new user.
-
- User's home directory is named after his/her login ID. Device "HOME:" is
- assigned to that directory (by commands Login or/and UserStartup) every
- time user logs in.
-
- The following directories and files are created to the <system's_home>
- (="HOMES:"):
-
- <id> (DIR) Created always. Assigned to "HOME:".
- mail (DIR) Created always.
- incoming Created always. Contains greetings mail.
- startup Created when switch STARTUP is present. Is empty.
- lock.<id> Created when switch LOCKS is present. Is empty.
- motd.<id> Created when switch MOTD is present. Is empty.
-
- <id> is the login ID of given user.
-
-
- ARGUMENTS
-
- HomeAdd P=PATH/K,ID,STARTUP/S,LOCKS/S,MOTD/S
-
- PATH
- <path>
- Path to the system's home (users' home directories are stored here).
- Default is "HOMES:".
-
- ID
- <login_id>
- User ID
-
- STARTUP
- Create default startup file.
-
- LOCKS
- Create empty lock file.
-
- MOTD
- Create individual default "message of to day" file.
-
-
- EXAMPLES
-
- HomeAdd jake
- HomeAdd jake STARTUP
- HomeAdd jake STARTUP LOCKS
- HomeAdd jake STARTUP MOTD
- HomeAdd S: jake STARTUP LOCKS MOTD
- HomeAdd S: jake STARTUP
- HomeAdd S: jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- HomeDel
- UserAdd
-
-
- 35. HomeDel
-
-
- NAME
-
- HomeDel
-
-
- REQUIREMENTS
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Superuser command only.
-
- Removes home directory of given user.
-
- The following directories and files are removed from <system's_home>
- (="HOMES:"):
-
- <id> (DIR)
- mail (DIR)
- incoming
- startup
- lock.<id>
- motd.<id>
-
- <id> is the login ID of given user.
-
-
- ARGUMENTS
-
- HomeDel P=PATH/K/A,ID/A
-
- PATH
- <path>
- Path to the system's home (users' home directories are stored here).
- Default is "HOMES:".
-
- ID
- <login_id>
- User ID
-
-
- EXAMPLES
-
- HomeDel jake
- HomeDel S: jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- HomeAdd
- UserDel
-
-
- 36. HostName
-
-
- NAME
-
- HostName
-
-
- REQUIREMENTS
-
- Evironment variables:
-
- "UserID" - to get current user login ID
- "HostName" - to get system's name
-
-
- DESCRIPTION
-
- Show or set computer's name.
-
-
- ARGUMENTS
-
- HostName HOST
-
- HOST - New name for your Amiga. Option available only for superuser.
-
- Without arguments HostName shows computer's name.
-
-
- EXAMPLES
-
- HostName
- HostName Amiga2000
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- -
-
-
- 37. Last
-
-
- NAME
-
- Last
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file "finger.log"
-
-
- Files:
-
- "ETC:finger.log" - to get last login information
-
-
- DESCRIPTION
-
- Show user's last login information.
-
-
- ARGUMENTS
-
- Last ID
-
- ID
- <login_id>
- User's ID for login information.
-
- Without argument Last shows every user's login information.
-
-
- EXAMPLES
-
- Last
- Last jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- FlushLog
- Login
-
-
- 38. ListUsers
-
-
- NAME
-
- ListUsers
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to list users
-
-
- DESCRIPTION
-
- List system's users.
-
- Output:
- <user_id>1 <user_real_name>1
- <user_id>2 <user_real_name>2
- <user_id>3 <user_real_name>3
- ...
- <user_id>n <user_real_name>n
-
- System have <number_of_users> users.
-
- where
-
- <user_id>
- User ID
-
- <user_real_name>
- The real name of user
-
- <number_of_users>
- Total number of system's users
-
-
- ARGUMENTS
-
- ListUsers
-
-
- EXAMPLES
-
- ListUsers
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Finger
- Last
- Mail
- UserAdd
- UserDel
- UserMod
- WhoIs
-
-
- 39. Login
-
-
- NAME
-
- Login
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - for files passwd and finger.log
- "HOMES:" - to find and set user home
-
-
- Files:
-
- "ETC:passwd" - to log in (user ID's and passwords are stored here)
- "ETC:finger.log" - to get last login and to save current login place,
- date, and time
-
-
- Commands:
-
- "alock" - for ALock login
- "alockpatch" - for ALock login
- "flushlog" - to flush log file
- "lock" - to lock and unlock drives
- "newmail" - to check mailbox contents
- "passwd" - to change password
- "readmotd" - to read MOTDs
- "userstartup" - to execute user's startup sequence
-
-
- Environment variables:
-
- "Kickstart" - to get kickstart version number
- "Workbench" - to get workbench version number
- "HostName" - to get system's name
-
-
- DESCRIPTION
-
- Login logs into a system.
-
- Login can be executed from Shell or Workbench. Both cases Login will
- open an own screen to read login ID and password. After successful
- login procedure, main menu will be opened (if NOMENU option was not
- present).
-
- Login uses preference file ("Login.prefs") if present. Only superuser
- can change preferences.
-
-
- ARGUMENTS
-
- Login A=ALOCK/K,E=SECURITY/K,F=FONTS/K,L=LOGIN/K,P=PASSWORD/K,
- R=RETRIES/N/K,S=SCREEN/K,NOBEEP/S,NOMENU/S
-
- CLI arguments and WorkBench tooltypes:
-
- ALOCK
- <alock_arguments>
- If any arguments are given, login will use ALock to log in.
- Arguments given here will be passed to the ALock command.
- Example: ALOCK=""
-
- SECURITY
- <hex_value>
- This argument controls Login security level. Default = 0.
- -----------------------------------------------
- Control bit Purpose
- -----------------------------------------------
- 0 Disable/enable ALock loging
- 1 Disable/enable default login ID
- 2 Disable/enable default password
- -----------------------------------------------
- When bit is set, option is disabled.
- Example: SECURITY="7"
-
- FONTS
- <name>,<size>
- Set fonts to be used in login procedure.
- <name> = font name with extension .font
- <size> = font size
- Example: FONTS="ruby.font,13"
-
- LOGIN
- <id>
- Set default login ID.
- Example: LOGIN="root"
-
- PASSWORD
- <password>
- Set default password.
- Example: PASSWORD="6qsiPuu"
-
- RETRIES
- <int_value>
- Set maximum number of login retries. When maximum retries limit is
- reached, Login will perform coldreboot. Default = 0 = no limit.
- Example: RETRIES=0
-
- SCREEN
- <hex_value>
- Set screenmode to use. Default = 08000.
- ------------------------------------
- Value Screenmode
- ------------------------------------
- 00000 Lores
- 00004 Lores-Interlaced
- 08000 Hires
- 08004 Hires-Interlaced
- 08020 SuperHires
- 08024 SuperHires-Interlaced
- 11000 NTSC:Lores
- 11004 NTSC:Lores-Interlaced
- 19000 = NTSC:Hires
- 19004 = NTSC:Hires-Interlaced
- 19020 = NTSC:SuperHires
- 19024 = NTSC:SuperHires-Interlaced
- 21000 = PAL:Lores
- 21004 = PAL:Lores-Interlaced
- 29000 = PAL:Hires
- 29004 = PAL:Hires-Interlaced
- 29020 = PAL:SuperHires
- 29024 = PAL:SuperHires-Interlaced
- 31004 = VGA-ExtraLores
- 31005 = VGA-ExtraLores-Interlaced
- 39004 = VGA-Lores
- 39005 = VGA-Lores-Interlaced
- 39024 = Productivity
- 39025 = Productivity-Interlaced
- 41000 = A2024_10Hz
- 49000 = A2024_15Hz
- ------------------------------------
- Example: SCREEN="08024"
-
- NOBEEP
- Do not flash screen when false login attempt occures.
- Example: NOBEEP
-
- NOMENU
- Do not open login menu.
- Example: NOMENU
-
-
- EXAMPLES
-
- Login
- Login >NIL:
- Login NOMENU SECURITY=7 RETRIES=5
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- FlushLog
- Last
- Passwd
- ReadMOTD
- UserStartup
-
-
- 40. Main menu
-
-
- Exit from Login.
-
-
- 41. Relogin
-
-
- Exit from Login.
-
-
- 42. Change password
-
-
- Exit from Login.
-
-
- 43. Exit
-
-
- Exit from Login.
-
-
- 44. Options menu
-
-
-
- OPTIONS
-
- ______________________________________
- | |
- | @| Enabled Mailbox check |
- | |
- | @| Enabled Show MOTD |
- | |
- | @| Enabled Show Individual MOTD |
- | |
- | @| Enabled Flush log |
- | |
- | @| Enabled Update log |
- | |
- | @| Enabled User startup |
- |______________________________________|
-
- Save Use Cancel
-
-
- Mailbox check
- Enable/disable mailbox check.
-
- Show MOTD
- Enable/disable viewing of "Message Of Today".
-
- Show Individual MOTD
- Enable/disable viewing of "Individual Message Of Today".
-
- Flush log
- Enable/disable log flushing. This option is for superuser (root) only.
-
- Update log
- Enable/disable log update. This option is for superuser (root) only.
-
- User startup
- Enable/disable user startup. This option is for superuser (root) only.
-
- Save
- Save options and exit to the main menu. This operation is allowed for
- superuser (root) only.
-
- Use
- Use these options and exit to the main menu.
-
- Cancel
- Undo changes and exit to the main menu.
-
-
- 45. Mail
-
-
- NAME
-
- Mail
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to send mail
-
-
- Environment variables:
-
- "UserID" - to send mail
- "HostName" - to send mail
-
-
- DESCRIPTION
-
- Send mail. Before sending mail, you have to write it by using some text
- editor and save it somewhere. After that you can send the mail.
-
-
- ARGUMENTS
-
- Mail SUBJECT/A,FILE/A,ID/A
-
- SUBJECT
- <mail_subject>
- Mail subject
-
- FILE
- <mail_file>
- Mail file name
-
- ID
- <login_id>
- Receiver's ID
-
-
- EXAMPLES
-
- Mail Hello ram:mail.txt jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- ListUsers
- MailBox
- NewMail
- ReadMail
- TrashMail
-
-
- 46. MailBox
-
-
- NAME
-
- MailBox
-
-
- REQUIREMENTS
-
- Devices:
-
- "HOME:" - to list mails
-
-
- Files:
-
- "HOME:mail/incoming" - to list mails
-
-
- DESCRIPTION
-
- List mailbox contents.
-
- If any keywords are given, MailBox will list only those messages which
- include any of the given keywords. (Keyword search is case sensitive.)
-
- Output:
- <message_number>1 <mmm>1 <dd>1 <sender>1 <length>1 <subject>1
- <message_number>2 <mmm>2 <dd>2 <sender>2 <length>2 <subject>2
- <message_number>3 <mmm>3 <dd>3 <sender>3 <length>3 <subject>3
- ...
- <message_number>n <mmm>n <dd>n <sender>n <length>n <subject>n
-
- where
-
- <message_number>
- Message number
-
- <mmm>
- Month
-
- <dd>
- Day
-
- <sender>
- Sender user ID
-
- <length>
- Mail length in bytes
-
- <subject>
- Subject
-
-
- ARGUMENTS
-
- MailBox M=MAILBOX/K,KEYWORDS/M
-
- MAILBOX
- <mailbox>
- Name of the mailbox (default is "HOME:mail/incoming")
-
- KEYWORDS
- <keyword_1> <keyword_2>... <keyword_n>
- List only messages including some or all of the keywords
-
-
- EXAMPLES
-
- MailBox
- MailBox greetings hello hi
- MailBox MAILBOX=HOME:mail/incoming amiga Amiga AMIGA
-
-
- BUGS
-
- None known.
-
- LOOK ALSO
-
- Mail
- NewMail
- ReadMail
- TrashMail
-
-
- 47. NewMail
-
-
- NAME
-
- NewMail
-
-
- REQUIREMENTS
-
- Devices:
-
- "HOME:" - to check mailbox
-
-
- Files:
-
- "HOME:mail/incoming" - to check mailbox
-
-
- Libraries:
-
- reqtools.library - for requester
-
-
- DESCRIPTION
-
- Check if user have received new mail.
-
- If mail exists the screen will flash and message "You have <n> mails."
- will appear (requester), where <n> is number of mails found. If option
- NOGUI exists, information is displayed in CLI window instead of
- requester.
-
- Ideal place for this command is in "Shell-startup".
-
-
- ARGUMENTS
-
- NewMail M=MAILBOX/K,NOBEEP/S,NOGUI/S
-
- MAILBOX
- <mailbox>
- The name of the mailbox (default is "HOME:mail/incoming")
-
- NOBEEP
- Do not flash screen when you have received mail.
-
- NOGUI
- Do not use requester to show number of mails received.
-
-
- EXAMPLES
-
- NewMail
- NewMail NOBEEP
- NewMail NOGUI
- NewMail MAILBOX="RAM:mail/incoming" NOBEEP NOGUI
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Mail
- MailBox
- ReadMail
- TrashMail
-
-
- 48. Passwd
-
-
- NAME
-
- Passwd
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to change password
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Change current user password.
-
- Passwd can be executed from CLI or Workbench. Both cases an own screen
- will be opened to ask current user password and new password. The
- following gadgets will appear:
- __________
- Password |__________| = current password
- __________
- New password |__________| = new password
- __________
- Verify |__________| = new password again for verifying
-
- By default new password must contain at least 6 characters and commas
- are not allowed as a password characters.
-
- Passwd uses preference file ("Passwd.prefs") if present. Only superuser
- can change preferences (-> PASSWDLEN).
-
-
- ARGUMENTS
-
- Passwd F=FONTS/K,P=PASSWDLEN/N/K,R=RETRIES/N/K,S=SCREEN/K,NOBEEP/S
-
- CLI arguments and WorkBench tooltypes:
-
- FONTS
- <name>,<size>
- Set fonts to be used.
- <name> = font name with extension .font
- <size> = font size
- Example: FONTS="ruby.font,13"
-
- PASSWDLEN
- <int_value>
- Set minimum length of new password. This option is for superuser (root)
- only.
-
- RETRIES
- <int_value>
- Set maximum number of password retries. When maximum retries limit is
- reached, Passwd will exit. Default = 6. Value 0 = unlimited retries.
- Example: RETRIES=3
-
- SCREEN
- <hex_value>
- Set screenmode to use. Default = 08000.
- ------------------------------------
- Value Screenmode
- ------------------------------------
- 00000 Lores
- 00004 Lores-Interlaced
- 08000 Hires
- 08004 Hires-Interlaced
- 08020 SuperHires
- 08024 SuperHires-Interlaced
- 11000 NTSC:Lores
- 11004 NTSC:Lores-Interlaced
- 19000 = NTSC:Hires
- 19004 = NTSC:Hires-Interlaced
- 19020 = NTSC:SuperHires
- 19024 = NTSC:SuperHires-Interlaced
- 21000 = PAL:Lores
- 21004 = PAL:Lores-Interlaced
- 29000 = PAL:Hires
- 29004 = PAL:Hires-Interlaced
- 29020 = PAL:SuperHires
- 29024 = PAL:SuperHires-Interlaced
- 31004 = VGA-ExtraLores
- 31005 = VGA-ExtraLores-Interlaced
- 39004 = VGA-Lores
- 39005 = VGA-Lores-Interlaced
- 39024 = Productivity
- 39025 = Productivity-Interlaced
- 41000 = A2024_10Hz
- 49000 = A2024_15Hz
- ------------------------------------
- Example: SCREEN=08024
-
- NOBEEP
- Do not flash screen when false password occures.
- Example: NOBEEP
-
-
- EXAMPLES
-
- Passwd
- Passwd FONTS="ruby.font,13" NOBEEP
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Login
- UserMod
-
-
- 49. ReadMail
-
-
- NAME
-
- ReadMail
-
-
- REQUIREMENTS
-
- Devices:
-
- "HOME:" - to read mail
-
-
- Files:
-
- "HOME:mail/incoming" - to read mail
-
-
- DESCRIPTION
-
- Extract new mail to the standard output.
-
- Mail number 0 is equal to the last mail number.
-
- Output:
- From: <userid>@<hostname>
- Subject: <subject>
- To: <userid> (<username>)
- Date: <weekday> <month> <day> <hour>:<minute>:<second> <year>
-
- <message>
-
- or (when NOHEADER-option present)
- <message>
-
-
- ARGUMENTS
-
- ReadMail M=MAILBOX/K,MAIL/N/A,NOHEADER/S
-
- MAILBOX
- <mailbox>
- Name of the mailbox (default is "incoming")
-
- MAIL
- <int_value>
- Mail number
-
- NOHEADER
- Do not show mail header
-
-
- EXAMPLES
-
- ReadMail 1
- ReadMail 1 NOHEADER
- ReadMail MAILBOX=home:mail/incoming 0
- ReadMail >RAM:last.txt 0 NOHEADER
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Mail
- MailBox
- NewMail
- ReadMOTD
- TrashMail
-
-
- 50. ReadMOTD
-
-
- NAME
-
- ReadMOTD
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read message of today
- "HOMES" - to read individual message of today
-
-
- Commands:
-
- "run" - when using default viewer
- "more" - when using default viewer
-
-
- Files:
-
- "motd" - to view the contents of "message of today"-file
- "motd.<id>" - to view the contents of "individual message of today"-file
-
-
- DESCRIPTION
-
- ReadMOTD will show the contents of "message of today"-files. Without
- any arguments the general MOTD-file will be shown ("ETC:motd"). Argument
- INDIVIDUAL will cause ReadMOTD to show the contents of "individual
- message of today"-file ("HOMES:motd.<id>").
-
- ReadMOTD doesn't have an own internal viewer, it always use external
- viewer to show file contents. By default external viewer is "more".
-
- Instead of text files ReadMOTD can show for example pictures, animations,
- and play samples. This can be done by giving correct player to the
- ReadMOTD.
-
-
- ARGUMENTS
-
- ReadMOTD VIEWER,INDIVIDUAL/S
-
- VIEWER
- <command>
- Command-line for for external viewer. Default is "run more %s".
- Template "%s" is replaced with correct file name ("motd" or "motd.<id>").
-
-
- INDIVIDUAL
- Read individual message of today
-
-
- EXAMPLES
-
- ReadMOTD
- ReadMOTD INDIVIDUAL
- ReadMOTD VIEWER="run >NIL: multiview SCREEN %s"
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Login
- ReadMail
-
-
- 51. TrashMail
-
-
- NAME
-
- TrashMail
-
-
- REQUIREMENTS
-
- Devices:
-
- "HOME:" - to trash mail
-
-
- Files:
-
- "HOME:mail/incoming" - to trash mail
-
-
- DESCRIPTION
-
- Trash mail.
-
- Mail number 0 is equal to the last mail number.
-
-
- ARGUMENTS
-
- TrashMail M=MAILBOX/K,MAIL/N/M/A
-
- MAILBOX
- <mailbox>
- Name of the mailbox (default is "home:mail/incoming")
-
- MAIL
- <int_value_1> <int_value_2>... <int_value_n>
- Mail number(s) to be removed
-
-
- EXAMPLES
-
- TrashMail 1
- TrashMail 1 3 4 7
- TrashMail MAILBOX=home:mail/incoming 0
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Mail
- MailBox
- NewMail
- ReadMail
-
-
- 52. UserAdd
-
-
- NAME
-
- UserAdd
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to get file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to add new user
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Superuser command only.
-
- Create new user. Use command "HomeAdd" the create home directory for
- new user.
-
-
- ARGUMENTS
-
- UserAdd I=ID/K,N=NAME/K,P=PASSWORD/K
-
- ID
- <login_id>
- User unique identification name.
-
- NAME
- <name>
- User's real name.
-
- PASSWORD
- <password>
- Password for new user.
-
-
- EXAMPLES
-
- UserAdd ID=jake PASSWORD="12345678" NAME="Janne Peräaho"
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- HomeAdd
- ListUsers
- UserDel
- UserMod
-
-
- 53. UserDel
-
-
- NAME
-
- UserDel
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to get file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to delete user
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Superuser command only.
-
- UserDel removes user from host computer. Use command "HomeDel" to remove
- user's home directory.
-
-
- ARGUMENTS
-
- UserDel ID/A
-
- ID
- <login_id>
- User's ID which you want to remove.
-
-
- EXAMPLES
-
- UserDel jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- HomeDel
- ListUsers
- UserAdd
- UserMod
-
-
- 54. UserMod
-
-
- NAME
-
- UserMod
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to get file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to modify user
-
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Superuser command only.
-
- Modify user information.
-
-
- ARGUMENTS
-
- UserMod I=ID/K,D=NEWID/K,N=NAME/K,P=PASSWORD/K
-
- ID
- <login_id>
- User's ID which userinformation you want to modify.
-
- NEWID
- <login_id>
- New user identification name.
-
- NAME
- <name>
- New real name for user.
-
- PASSWORD
- <password>
- New password for user.
-
-
- EXAMPLES
-
- UserMod ID=jake NEWID=jake PASSWORD="12345678" NAME="Janne Peräaho"
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- ListUsers
- UserAdd
- UserDel
-
-
- 55. UserStartup
-
-
- NAME
-
- UserStartup
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - for file passwd
- "HOMES:" - for locking and executing startup
-
-
- Files:
-
- "ETC:passwd" - to check current user login ID
-
-
- Environment variables:
-
- "UserID" - to assign home directory and to execute correct startup
- sequence
-
-
- Commands:
-
- "lock" - to lock drives
- "execute" - to execute startup sequence
-
-
- DESCRIPTION
-
- With "UserStartup" it's possible to add individual startup-sequences for
- each system user.
-
- Individual startup sequence can be found from user's home directory:
- "HOME:startup" = "HOMES:<id>/startup" = "<system's_home>/<id>/startup".
-
- Device "HOMES:" should be assigned before executing UserStartup. If it's
- not assigned, path to the system's home is required.
-
- UserStartup try always assign device "HOME:" to "HOMES:<id>" or
- "<path>/<id>", where <id> is current user login ID and <path> is path to
- the system's home.
-
- It is also possible to lock drives from certain users by adding a file
- named after user's login ID in system's home ("HOMES:lock.<id>"). This
- file contains the names of the drives which should be write protect for
- this user.
-
- Each drive name have it's own line in that file. Locking is not
- permanent. Either reboot or new login will release the locks.
-
-
- ARGUMENTS
-
- UserStartup PATH
-
- PATH
- <path>
- Path to the system's home.
-
-
- EXAMPLES
-
- UserStartup
- UserStartup HOMES:
- UserStartup S:
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Login
-
-
- 56. WhoAmI
-
-
- NAME
-
- WhoAmI
-
-
- REQUIREMENTS
-
- Environment variables:
-
- "UserID" - to get current user login ID
-
-
- DESCRIPTION
-
- Show current user's identification name.
-
-
- ARGUMENTS
-
- WhoAmI
-
-
- EXAMPLES
-
- WhoAmI
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Finger
- ListUsers
- WhoIs
-
-
- 57. WhoIs
-
-
- NAME
-
- WhoIs
-
-
- REQUIREMENTS
-
- Devices:
-
- "ETC:" - to read file "passwd"
-
-
- Files:
-
- "ETC:passwd" - to get information about given user
-
-
- DESCRIPTION
-
- Show user's real name.
-
-
- ARGUMENTS
-
- WhoIs ID/A
-
- ID
- <login_id>
- User's ID which real name you want to know.
-
-
- EXAMPLES
-
- WhoIs jake
-
-
- BUGS
-
- None known.
-
-
- LOOK ALSO
-
- Finger
- ListUsers
- WhoAmI
-
-
- 58. Limitations
-
-
- ALockUtils Version 1.1
-
- Limitations
-
-
- Security gained through ALock is far from perfect, but it offers excellent
- basic security solutions for average users.
-
- Main weak points are unprotected password file and OS's ability to prevent
- startup-sequence execution when required.
-
- With ALockUtils communication between users is possible by using individual
- mailbox files. However, these mailboxes are not protected from other users.
- Anyone have access to everyones mailboxes.
-
- Password- and mailbox file problems can be solved by using cryptographic
- procedures, but I am not willing to carry out file encoding and decoding
- qualities without users request.
-
-
- 59. History
-
-
- ALockUtils Version 1.1
-
- History
-
- 09.05.1996
-
- ALockUtils version 1.0. First release.
-
- 15.09.1996
-
- ALockUtils version 1.1. Second release.
-
- NEW
-
- - Login can now fully replace ALock
- - install scripts for ALock and ALockUtils
- - Login
- + GUI
- + ability to change password
- + login options
- + default ID and password
- + security levels
- + ALock logging
- + user defined number of retries
- + preference file
- - command ReadMOTD
- - UserStartup
- + default path to the system's home
-
- BUG FIXES
-
- - Login
- + bug in "last login"-procedure (gave first login) fixed
- + security problem (command-line buffer) in CLI login fixed
- - Finger
- + bug in "last login"-procedure (gave first login) fixed
-
-
- 60. Comments
-
-
- ALockUtils Version 1.1
-
- Comments
-
-
- ______
- | |\
- | ~~~ ¯|
- | ~~~ ~ |
- | ~ ~~~ |
- | ~~ ~ |
- | ~ ~ ~ |
- ¯¯¯¯¯¯¯
- COMMENTS
-
- 28.04.96 Jon Peterson
- Janne, great work supporting other authors with add-ons.
-
-
- 61. Future
-
-
- ALockUtils Version 1.1
-
- Future
-
-
- . .
- _ \_/ _
- \(_)/
- -=(_)=-
- _/(_)\_
-
- BUG OBSERVATIONS
-
-
- _____
- |_____\ ____ ____
- | | __|____|____
- | | _|____|____|__
- |_| |____|____|____|
-
- DEVELOPMENT PROPOSALS
-
- 09.05.96 Janne Peräaho
- GUIs for receiving and sending mails, adding, modifying, and deleting
- users
-
- 15.09.96 Janne Peräaho
- Preference file for command ReadMOTD
-